Centralizing Project Definitions

Most code projects are worked on by more than one person. For reasons of efficiency and consistency, it is recommended that one person sets up the Helix QAC project, and then distributes it to anyone else who needs it. The work done by the first person to ensure that all the correct options have been selected, does not then need to be repeated by the others.

A project definition is just a configuration file, and can be shared through a source control system, or simply by copying. However, using Helix QAC Dashboard to share these configurations has the advantage of unifying the project so that, on the Helix QAC Dashboard server, it has both the Helix QAC Dashboard project configuration and a stored Helix QAC configuration. The Helix QAC part of the Unified project can be downloaded onto a local machine. A permanent link is maintained between the local project and the project on the Helix QAC Dashboard server. This link helps with both uploading results and downloading baselines and suppressions.

Although, you can create multiple configurations for a project within Helix QAC, so that you can switch between ACFs, RCFs and CCTs within the one project, it is only possible to unify a project that has a single configuration (refer to The Helix QAC Dashboard Menu).